Receiving an access key

ABSTRACT

In an embodiment a secure module is provided that provides access keys to an unsecured system. In an embodiment the secure module may generate passcodes and supply the passcodes to the unsecured system. In an embodiment the access keys are sent to the unsecured system after receiving the passcode from the unsecured system. In an embodiment, after authenticating the passcode, the secure module does not store the passcode in its memory. In an embodiment, the unsecured module requires the access key to execute a set of instructions or another entity. In an embodiment, the unsecured system does not store access keys. In an embodiment, the unsecured system erases the access key once the unsecured system no longer requires the access key. In an embodiment, the unsecured system receives a new passcode to replace the stored passcode after using the stored passcode. Each of these embodiments may be used separately.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. patent application Ser. No. 11/134,123, entitled “Using an Access Key”, filed May 20, 2005, now abandoned which in turn is a continuation-in-part of U.S. patent application Ser. No. 11/131,652, entitled “Method of Generating Access Keys”, filed May 17, 2005, now U.S. Pat. No. 7,979,716 which in turn claims priority benefit of U.S. Provisional Patent Application No. 60/637,536, entitled, “Secure Keys,” filed Dec. 20, 2004, and claims priority benefit of U.S. Provisional Patent Application No. 60/646,463, entitled “Passcode Generator,” filed Jan. 24, 2005, and U.S. patent application Ser. No. 11/131,652, entitled “Method of Generating Access Keys,” filed May 17, 2005, is in turn a continuation-in-part of U.S. patent application Ser. No. 11/106,930, entitled “API For a System Having a Passcode Authenticator,” filed Apr. 14, 2005, now U.S. Pat. No. 7,707,622 which in turn is a continuation-in-part of U.S. application Ser. No. 11/106,183, entitled, “Interfacing With a System That Includes a Passcode Authenticator,” filed Apr. 13, 2005, now U.S. Pat. No. 7,702,911 which in turn is a continuation-in-part of U.S. patent application Ser. No. 11/104,357, entitled, “System for Generating Requests to a Passcode Protected Entity,” filed Apr. 12, 2005, now U.S. Pat. No. 7,886,155 which in turn is a continuation-in-part of U.S. patent application Ser. No. 11/104,343, entitled “Generating Requests For Access To a Passcode Protected Entity,” filed Apr. 11, 2005, now abandoned which in turn is a continuation-in-part of U.S. patent application Ser. No. 11/102,407, entitled “System For Handling Requests For Access To a Passcode Protected Entity,” filed Apr. 7, 2005, now abandoned which in turn is a continuation-in part of U.S. patent application Ser. No. 11/100,803, entitled, “Determining Whether to Grant Access to a Passcode Protected System,” filed Apr. 6, 2005, now U.S. Pat. No. 7,669,236 which in turn claims priority benefit of U.S. Provisional Patent Application No. 60/637,536, entitled “Secure Keys,” filed Dec. 20, 2004 and claims priority benefit of U.S. Provisional Patent Application No. 60/646,463, entitled “Passcode Generator,” filed Jan. 24, 2005; this application is a continuation-in-part of U.S. patent application Ser. No. 11/100,803, entitled, “Determining Whether to Grant Access to a Passcode Protected System,” filed Apr. 6, 2005; now U.S. Pat. No. 7,669,236 this application is also a continuation-in-part of U.S. patent application Ser. No. 11/106,930, entitled “API For a System Having Passcode Authenticator” filed Apr. 14, 2005; now U.S. Pat. No. 7,707,622 this application is also a continuation-in-part of U.S. patent application Ser. No. 11/131,652, entitled, “Method of Generating Access Keys,” filed May 17, 2005; now U.S. Pat. No. 7,979,716 additionally, this application claims priority benefit of U.S. Provisional Patent Application No. 60/637,536, “Secure Keys,” filed Dec. 20, 2004, which is incorporated herein by reference; and this application also claims priority benefit of U.S. Provisional Patent Application No. 60/646,463, entitled “Passcode Generator,” filed Jan. 24, 2005. All of the above applications are incorporated herein by reference. This application incorporates herein by reference U.S. Provisional Patent Application No. 60/629,868, entitled, “Finger Print Quality Assurance,” filed Nov. 18, 2004. This application also incorporates herein by reference U.S. Provisional Patent Application No. 60/631,199, entitled “Fingerprint Quality Assurance,” filed Nov. 26, 2004.

This application also incorporates herein by reference U.S. patent application Ser. No. 10/778,503, entitled “FPALM Fingerprint Authentication Lock Mechanism,” filed Feb. 15, 2004. This application also incorporates herein by reference U.S. patent application Ser. No. 10/889,237, entitled “FPALM II Fingerprint Authentication Lock Mechanism II,” filed Jul. 11, 2004.

FIELD

The specification generally relates to a security access system.

BACKGROUND

In typical cryptographic systems, one or more encryption keys are created on the sender's computer or device and are used to transit an encrypted message to another computer or device. The receiver also has one or more encryption keys to decrypt the message. Typical encryption keys have a length of 128 bits, 256 bits, 512 bits, 2048 bits or sometimes larger. Since most people are incapable of remembering an encryption key this long, these encryption keys are stored on a computer or other device that often requires a shorter, less secure, password to access. This creates a situation, where the password is often much easier to obtain than the encryption keys. Furthermore, many operating systems have many security flaws, so often a sophisticated intruder does not have to obtain the password. The intruder can gain access to the computer containing the encryption keys, and the cryptographic system's security is compromised.

It is possible to scan fingerprints into computers, rather than enter a password, to access computers. However, such systems are unsecure, because the fingerprints, or derived fingerprint information, can be captured by an intruder. Consequently, the security of the whole system is compromised.

Some Advantages Over Other Systems

The decentralization of the security makes the systems and methods presented here, more secure and helps preserve the user's privacy. Privacy is important in regard to preventing identity theft. In some inferior security systems, the keys are pre-programmed during a particular time of manufacturing. This creates a centralized point of security that can be exploited by hackers and criminals. They can reverse engineer the devices and figure out what the keys are. With this decentralization of the system, the creation of the keys for a particular user or device is localized. This decentralization of the security helps prevent catastrophic break-ins or breaches. These types of catastrophic security breaches for inferior systems are all to common as hackers and terrorists have universal access to many critical systems via the Internet.

This decentralization of the security also enhances the usability of the system. In some inferior systems, administrators set up the keys and perform various “personalizations.” For these types of inferior systems, the logistics of the IT support on thousands or millions or tens of millions of users is so cumbersome that they are unusable. For example, a credit card company may issue 100 million cards that require administrators for the administrator keyes, which can create an administrative nightmare in addition to giving the administrator access to personal information of a substantial number of people. An administrator with access to personal information may also create a big security and identity theft risk. One of Biogy's advantages is that the keys are generated locally in the field via a user-implemented process, based on the uniqueness of the user. This creates a unique and decentralized key generation, which also prevents hackers and thieves from carrying out a massive attack on millions of cards. As an analogy for Biogy's superior security by decentralization, consider that terrorists might want to cripple the U.S. energy supply, economy or military. There is greater security in having 100,000 small energy resources—analogous to the user implemented initialization—decentralized uniformly across the U.S. rather than having, for example, three giant oil refineries and/or three large nuclear power plants providing all of our energy needs. Using three giant oil companies and/or three nuclear power plants is analogous to inferior systems using a centralized, administrator-implemented set up.

Another advantage is that in some embodiments the passcodes used here are temporary. In this case, they are more difficult to compromise. In some embodiments with a wireless device, the passcode may be transmitted wirelessly and the passcode may last a few microseconds or a few seconds. In some embodiments, the passcode may appear on a display screen of a flash drive, smart card, or a mobile phone or PDA. This passcode may last a few seconds or written down by the user and used in a few hours—before it is typed in and no longer in use. In some embodiments, a mobile device may run on a battery or solar power, where the passcode may be automatically transmitted through a USB, micro USB port or some other hardware port. If the device is authenticated in a user's hands where it is not yet plugged into the port, then the passcode may last a few seconds or a few minutes before it is plugged into the port.

BRIEF DESCRIPTION OF THE DRAWINGS

In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples of the invention, the invention is not limited to the examples depicted in the figures.

FIG. 1 shows a block diagram of a system for encrypting and decrypting items.

FIG. 2 shows a block diagram of an example of an unsecured system, which may be used in the system of FIG. 1.

FIG. 3 shows a block diagram of an example of the memory of FIG. 2.

FIG. 4 shows an example of an embodiment of a secure system.

FIG. 5 shows an example of a secure module.

FIG. 6 shows an example of a secure module.

FIG. 7 shows an example of a secure module.

FIG. 8 shows a flowchart of an example of a method for assembling a secure module.

FIG. 9 shows a flowchart of an example of a method of setting up the system of FIG. 1.

FIG. 10 shows a flowchart of an example of a method of encrypting and decrypting data.

FIG. 11 shows a flowchart of an example of a method of encrypting or decrypting data.

DETAILED DESCRIPTION

Although various embodiments of the invention may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments of the invention do not necessarily address any of these deficiencies. In other words, different embodiments of the invention may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies that may be discussed in the specification, and some embodiments may not address any of these deficiencies.

In general, at the beginning of the discussion of each of FIGS. 1-7 is a brief description of each element, which may have no more than the name of each of the elements in the one of FIGS. 1-7 that is being discussed. After the brief description of each element, each element is further discussed. In some of FIGS. 1-7 the further discussion of each element is usually in the numerical order of the elements. In some of FIGS. 1-7 the further discussion of each element discusses a group of the elements together. In some of FIGS. 1-7 after the further discussion of each element, there is a discussion of how all the elements cooperate with one another. In general, each of FIGS. 1-10 is discussed in numerical order, and the elements within FIGS. 1-10 are also usually discussed in numerical order to facilitate easily locating the discussion of a particular element. Nonetheless, there is no one location where all of the information of any element of FIGS. 1-10 is necessarily located. Unique information about any particular element or any other aspect of any of FIGS. 1-10 may be found in, or implied by, any part of the specification.

FIG. 1 shows a block diagram of system 100 for encrypting and decrypting items. System 100 includes a secure module 102 and acquisition mechanism 104, which includes secure area 106. Secure area 106 may include encryption key circuitry 108 having memory 110. Memory 110 may include instructions 112, which may include instructions for acquire user data 114, compare user data 116, and store user data 118. Memory 110 may also include user information 120 and encryption key 122. Instructions 112 may also include generate encryption keys 123. Secure module 102 may also include interface 124. System 100 may also include unsecured system 126, which runs encryption instructions 128. In other embodiments system 100 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Secure module 102 may include any of a number of systems. In an embodiment, secure module 102 is configured so that it is difficult to access the inner working of secure module 102. In other words, secure module 102 may be configured so that it is difficult to examine and/or alter the contents of any memory within secure module 102 and/or to send commands to secure module 102.

Acquisition mechanism 104 may be a sensor, and may enable secure module 102 to acquire (e.g., scan in or receive) user data, such as fingerprints, other biometric data, or other user data. For example, if acquisition mechanism 104 includes a fingerprint sensor, acquisition mechanism 104 may include an area sensor or a sweep sensor.

Secure area 106 is a region within secure module 102 within which various security measures have been implemented. For example, the security of the secure area 106 may be enhanced by any one of, any combination or of, or all of (1) the use of embedded software, (2) the lack of an operating system, and (3) the secure area being at least part of a self-contained device separate from unsecured system 126. For example, the unit that includes the secure area 106 (e.g., secure module 102) may contain its own processor.

Encryption key circuitry 108 generates encryption keys and may have other functions. Encryption key circuitry 108 may include circuitry configured for generating encryption keys or may include a processor configured (e.g., programmed) for generating encryption keys. Encryption key circuitry 108 may include a combination of a processor and specialized circuitry configured for performing a particular method or computation. Encryption key circuitry 108 may communicate with acquisition mechanism 104 and with a host computer. Although not necessary, in some embodiments, acquisition mechanism 104 and encryption key circuitry 108 could be integrated into a single chip. Alternatively, acquisition mechanism 104 and encryption key circuitry 108 may be in two separate chips. Throughout this specification encryption key circuitry 108 may be replaced with access key circuitry to obtain different embodiments.

Memory 110 may be incorporated within encryption key circuitry 108 and may include volatile and nonvolatile memory. The use of non-volatile memory enables the secure module 102 to permanently store user information, executable code, and/or encryption keys. In some embodiments, the memory 110 is on (e.g., “onboard”) encryption key circuitry 108. Memory 110 may include embedded instructions that are executed by encryption key circuitry 108.

Instructions 112 are stored on memory 110, and may include embedded instructions executed by encryption key circuitry 108. Instructions 112 may be capable of generating passcodes (e.g., a password) based on user data. In this specification the word passcode is generic to the word password in that a passcode can be any code. Throughout this specification, the word passcode may be replaced by the word password to obtain a specific embodiment. The passcodes may be caused to be sent to an unsecured device and/or to be used to authenticate a passcode received from an unsecured device. Instructions 112 may be capable of generating encryption keys based on user data and/or passcodes based on encryption keys. Instructions 112 may also be capable of authenticating a set of newly acquired user data (e.g., fingerprints) by comparing the newly acquired user data with stored user information (e.g. stored characteristics of fingerprints).

Acquire user data 114 may include instructions for acquiring a fingerprint and/or other user data from acquisition mechanism 104. Compare user data 116 may include instructions for comparing and/or matching acquired user data with stored user information. Store user information 118 may include instructions for storing user information acquired by acquire user data 114 from acquisition mechanism 104.

User information 120 may be the user data acquired by acquire user data 114. Alternatively, user information 120 may include information derived from the user data acquired using acquire user data 114. For example, if acquisition mechanism 104 acquires fingerprints, user information may include information characterizing the fingerprints instead of, or in addition to, the actual fingerprints. User information 120 may be, or may be based upon, many other types of user data in addition to, or instead of, fingerprints. For example, user information 120 may include a name, a birthday, a favorite number, a social security number, a driver's license, a profile, an image of a face, an iris scan, a toe print, a handprint, and/or a footprint. In an embodiment, the item used to generate the passcodes is any item that is unique. In an embodiment, the item used to generate the passcode is one that is difficult to fabricate, guess, find by trial and error, and/or compute. In an embodiment, the item used to generate the passcodes is uniquely associated with the user. In an embodiment, the item used to generate the passcodes has an unpredictable element to it (e.g., the unpredictable manner in which the patterns of lines in fingerprints differ between fingerprints).

As explained in U.S. patent applications Ser. No. 11/100,803, Ser. No. 11/102,407, Ser. No. 11/104,343, Ser. No. 11/104,357, and Ser. No. 11/106,183, and Ser. No. 11/106,930, any sequence of bits (which may represent any string of symbols) may be used as a passcode. In some cases, the passcode may be directly transmitted to another system without human intervention, and therefore the sequence of bits may not have a visual display in standard formats such as ASCII, Unicode, and so on. For example, the first sequence of 8 bits in the passcode could, in ASCII, represent the end of file character, which currently does not have a visual representation. In other embodiments where the passcode is displayed as a sequence of symbols on a graphical display, the symbols may be chosen from any subset of, or combination of, alphanumeric symbols, punctuation symbols, picture symbols, math symbols, upper case symbols, and/or lower case symbols, for example. The choice of alphanumeric symbols may include characters from a multiplicity of languages. An example of an alphanumeric passcode with 8 symbols 4R1pa5Wx. An example of a possible passcode with 8 symbols is

An example with 16 symbols including punctuation and other symbols is &x#W

q61!j$uS_m.

Encryption keys 122 may include one or more encryption keys, which are codes (sequences of bits or symbols) that are used for generating passcodes. Encryption keys 122 may be used by an encryption algorithm to encrypt and/or decrypt data. In this specification, encryption keys 122 may also be represented by the symbol K_(d). Encryption keys 122 may be stored on secure module 102. Encryption keys 122 may be stored in the internal memory (e.g., memory 110) of encryption key circuitry 108. One or more fingerprint images and/or other user data may be used to determine values for encryption keys 122. Using user information 120 to create encryption keys 122 helps ensure that the encryption key of each user is unique. Encryption keys 122 may be used as seed values for an encryption method that is implemented on an unsecured system. In another embodiment, encryption keys 122 are not used as seed values, but are just an access code, which may be referred to as an access key, for a method or other entity associated with the unsecured system.

Encryption keys 122 may be used as the registration code and/or the passcode generator of U.S. patent applications Ser. No. 11/100,803, Ser. No. 11/102,407, Ser. No. 11/104,343, Ser. No. 11/104,357, Ser. No. 11/106,183, and Ser. No. 11/106,930. Thus, similar to the passcode, any sequence of bits or sequence of symbols may be used as one of encryption keys 122. In some cases, encryption keys 122 may be directly transmitted without human intervention, and consequently the sequence of bits may not have a visual display in standard formats such as ASCII, Unicode, and so on. For example, the first sequence of 8 bits in one of encryption keys 122 could, in ASCII, represent the end of file character, which currently does not have a visual representation. In other embodiments where the encryption keys 122 are displayed as a sequence of symbols on a graphical display, the symbols may be chosen from any subset of or combination of alphanumeric symbols, punctuation symbols, picture symbols, math symbols, upper case symbols, and/or lower case symbols, for example. The choice of alphanumeric symbols may include characters from a multiplicity of languages. An example of an encryption key with 16 symbols is 1Ae58GnZbk3T4pcQ, and an encryption key with punctuation and other symbols may also be used. An example with 32 symbols is 1!56hs#K

3_(—)4xP*7:y2iW=K;r.+4vN?. There may be at least one encryption key for each user, secure module 102, and/or unsecured system 126. The same criterion and/or restrictions may be used for both passcodes and encryption keys 122 for determining what sequences of characters are valid. Throughout this specification encryption keys may be replaced with access keys to obtain different embodiments. Each of encryption keys 122 may have different parts stored in different locations within memory 110.

Generate encryption keys 123 is a method for generating encryption keys 122 using user information 120. Although in FIG. 1 generate encryption keys 123 is depicted as separate from instruction 112, generate encryption keys 123 may be included within instructions 112. Generate encryption keys 123 may implement a method that uses user information 120 as a seed for generating encryption keys 122.

Generate encryption keys 123 may be a “one-way” method, which is a method for which finding an inverse or for which finding the input based on the output is expected to be difficult or intractable. Throughout this specification generate encryption keys 123 may be replaced with instructions for generating access keys to obtain a different embodiment. Stated differently, a one-way method Φ has the property that given an output value z, it is not possible or computationally extremely difficult to find an input (e.g., message) m_(z) such that Φ(m_(z))=z. For some one-way functions, it could take over 10³⁰ years of computer processor execution time to compute Φ⁻¹(z). In other words, a one-way method Φ is a method that can be easily computed, but that has an inverse Φ⁻¹ that is extremely difficult (e.g., impossible) to compute. One manner of quantifying the difficulty of finding m_(z) (given an output z) is to use the number of computations that are expected to be required to compute and/or guess m_(z). For one type of method, it is expected to take between O(2^(n/2)) and O(2^(n)) (e.g. between 2^(n/2) and 2^(n)) computational steps to find or guess m_(z), (depending on the how clever the one performing the computations is), where n is the number of bits in the output z. The method Φ (which may be referred to as a generating method) may be a one-way algorithm, a one-way function, and/or another one-way method. By using a one-way method for computing encryption keys 122, even if one of encryption keys 122 is intercepted, stolen, or otherwise obtained, it is unlikely that the encryption key can be used to discover user information 120 or (if user information 120 was derived from user data) used to discover the user data from which user information 120 was derived.

One set of methods that may be used are one-way methods in which finding the inverse involves an operation that is mathematically indeterminate, impossible, intractable, computationally impractical, or computationally difficult. For example, one method is to use a collection of step functions each of whose domain and range is [0, 1, 2, . . . 255] and apply a distinct one of the step functions to a part of user information 120. User information 120 could be used to determine which step functions to select from the collection. If 16 step functions are chosen from the collection, then this would create an output having 128 bits. If n step functions are chosen from the collection, then this would create an output of 8 n bits. An alternative to selecting the step function would be to construct 32 matrices resulting from the step functions and compute the determinant modulo 256 for each of the 32 matrices. This creates a one-way method whose output is 256 bits.

As another example, one-way method Φ could involve first representing user information 120 by a string of digits. Then, each digit of the string of digits could be multiplied by a corresponding digit from another string of digits, where at least one digit of the other string has a value of zero. The inverse of this method would involve at least one division by zero for each multiplication by a digit with the value of zero, which has no inverse, and consequently this method would also be one-way. Similarly, functions for which finding their inverses involves computing a non-convergent series or non-convergent integral are other examples of classes of functions that may be used as one-way methods.

Another class of one-way methods involves computations that cause a loss of information or a discarding of selected pieces of information. Since some of the input information is lost in computing this class of one-way methods, the original input information (e.g., user information 120) is difficult and may be impossible to recover. For example, a one-way method may be constructed by first performing a randomizing operation such as discarding random bits of information from the input, adding random bits of information to the input, and/or performing another randomizing operation to the input, and then another method (e.g., function) may be applied to the information retained. Similarly, the same randomizing operations may be performed on the output of the one-way method.

In an embodiment, generate encryption key 123 includes a hash function. A “hash function,” denoted Φ, is a function that accepts as its input argument an arbitrarily long string of bits (or bytes) and produces a fixed-size output. In other words, a hash function maps a variable length input m to a fixed-sized output, Φ(m). Typical output sizes range from 128 to 512 bits, but can also be larger or smaller. An ideal hash function is a function Φ whose output is “uniformly distributed.” In other words, suppose the output size of Φ is n bits. If the message m is chosen randomly, then for each of the 2^(n) possible outputs for z, the probability that Φ(m)=z is 2^(−n). In an embodiment, the hash functions used in generate encryption key 123 are one-way.

In contrast to an ideal bash function, if the input m is chosen randomly, then for each of the 2^(n) possible outputs for z, the probability that Φ(m)=z is a value P, which is compared to 2^(−n). In an embodiment, the hash function is designed so that P is relatively close to 2^(−n). How close P is to 2^(−n) is a measure of the quality of the hash function. The chi-square function on n−1 degrees of freedom is a useful way to measure the quality of a real hash function. One uses a chi-square on n−1 degrees, because there are n bits of output. A confidence level that the real hash function is close to an ideal hash function (or has a certain quality) can be computed based on the chi-square function. Some typical confidence levels could be at least 90%, at least 95%, at least 99%, at least 99.5%, at least 99.999%, or greater depending on the level of security desired. In an embodiment, these confidence levels may represent a confidence that at least 2^(n/100) to 2^(n) computations are required to find the inverse of the hash function. In another embodiment, the above confidence levels represent a confidence that at least 2^(n/2) to 2^(n) computations are required to find the inverse of the hash function. In an embodiment, these confidence levels may represent a confidence that at least 2^(log(n)) to 2^(n) computations are required to find the inverse of the hash function. In an embodiment, these confidence levels may represent a confidence that at least 0.9(2^(n)) to 2^(n) computations are required to find the inverse of the hash function. In an embodiment, the hash functions that are used are one-way. Other types of one-way functions or methods may be used in place of a hash function.

Any of a number of hash functions may be used for one-way method Φ. One possible hash function is SHA-256, designed by the National Security Agency and standardized by the NIST, [NIST_STANDARDS_(—)1995], which is incorporated herein by reference. The output size of SHA-256 is 256 bits. Other examples of alternative hash functions are of those that are of the type that conforms to the standard SHA-1, which produces output values of 128 bits, and SHA-512, which produces output values of 512 bits, see [NIST_STANDARDS_(—)2001], which is incorporated herein by reference.

There are different methods that may be used for hashing user information 120, such as fingerprints. Different types of methods of hashing user information 120 are appropriate for different sizes of encryption keys, and different types of user information 120 that may be passed to the hash function. One method is to take two different pieces of user information 120 (e.g., two fingerprints) and apply the hash function SHA-256 to each piece of user information 120. For ease of explanation, denote the hash function SHA-256 as Φ₁. Each application of Φ₁ to user information 120 produces an output value of 256 bits. With two pieces of user information 120, (e.g., two fingerprints), these bits are concatenated together to create a 512-bit encryption key, called K_(d). Another method is to use two different sections S and T of a single acquired set of pieces of user data (e.g., two sections of one fingerprint), and produce a 512-bit encryption key, K_(d), by concatenating Φ₁(S) and Φ₁(T). An enhancement of this method can be used to create encryption keys larger than 512-bits. Divide one acquired piece of user information 120 (e.g., one fingerprint) into n sections: S₁, S₂, . . . , S_(n). Then concatenate the bits Φ₁(S₁), Φ₁(S₂), . . . , Φ₁(S_(n)). This creates an encryption key K_(d) that is 256 n bits in length. For example, if user information 120 is divided into 10 sections, then this method would create an encryption key with 2,560 bits.

Another embodiment is to use two different parts of user information, denoted S₁ and S₂, apply a one-way function Φ to each part of the finger print information to form fingerprint information that has the same length as each of the parts. For example, let the symbol ⊕ denote the exclusive-or function i.e. as a binary operator on bits 0⊕0=1⊕1=0 and 1⊕0=0⊕1=1. ⊕ is extended coordinate-wise to strings of bits; as an example, if A=0011 and B=0101, then A⊕B=0110. In an embodiment, a one-way function Φ is applied to each part and then take an exclusive-or, ⊕, of the two results. In other words, the encryption key is K_(d)=Φ(S₁)⊕Φ(S₂). If Φ has an output size of m bits, then K_(d) has a size of m bits. A similar process could be performed using other operators in place of an exclusive-or to create an encryption key K_(d) having a size of m bits.

Similarly, to create a larger key, start with 2n pieces of user information, S₁, S₂, . . . , S_(2n). Create n different m-bit keys, k₁, k₂, . . . k_(n) where k₁=Φ(S₁)⊕Φ(S₂), k₂=Φ(S₃)⊕Φ(S₄), k₃=Φ(S₄)⊕Φ(S₅), . . . , k_(n)=Φ(S_(2n-1))⊕Φ(S_(2n)). Then create the key K_(d) by concatenating these n keys; in other words, K_(d)=k₁k₂k₃ . . . k_(n). Thus, K_(d) has a size of mn bits, where the output of one-way function Φ is m bits. If Φ=Φ₁ (i.e. SHA-256), then K_(d) has a size of 256 n bits. A similar process could be performed using other operators in place of an exclusive-or to create an encryption key K_(d) having a size of mn bits.

Hash functions are discussed in [NIST_STANDARDS_(—)1995] National Institute of Standards and Technology, Secure Hash Standard, Apr. 17, 1995, FIPS PUB 180-1, [e.g., Page 88] and in [NIST_STANDARDS_(—)2001] National Institute of Standards and Technology, Secure Hash Standard, (draft) 2001, Draft FIPS PUB 180-2, [e.g., Page 89], which are each incorporated herein by reference. Hash functions are also discussed in U.S. patent applications Ser. No. 11/100,803, Ser. No. 11/102,407, Ser. No. 11/104,343, Ser. No. 11/104,357, and Ser. No. 11/106,183, and Ser. No. 11/106,930.

Although instructions 112, user information 120, encryption keys 122 and generate encryption keys 123 are depicted as contiguous blocks within memory 110, they may be stored in locations that are interdispersed amongst each other. Similarly, although instructions for acquire user data 114, compare user data 116, and store user data 118 are depicted as separate blocks within instructions 112, they may be stored in locations that are inter-dispersed amongst each other. Also, although instructions for acquire user data 114, compare user data 116, store user data 118, and generate encryption keys 123 are depicted at contiguous blocks, they may be lines of codes that are inter-dispersed amongst one another, and may not be separate program units.

Interface system 124 is used to communicate with unsecured system 126. Interface system 124 may be any one of and/or any combination of a USB port, an RS 232 connection, a wireless connection (e.g., using RFID), a serial port, and/or any of a number of other types of connections.

Unsecured system 126 may be a host computer, encryption device, or other machine that is used for encrypting data. The word “host” refers to a laptop, desktop, other type of computer, or possibly another electronic device. Unsecured system 126 may be a single module or a large system having many components. Unsecured system 126 is referred to as “unsecured” only because, in an embodiment, no steps are necessarily taken to secure unsecured system 126. However, unsecured system 126 may have been secured, and may have any combination of security safeguards protecting it. For example, unsecured system 126 may require entry of a passcode and/or any type of user data (e.g., any of the user data upon which user information 120 may be based) prior to entry. Alternatively, unsecured system 126 may have no security features.

Encryption instructions 128 may be executed by unsecured system 126, and may be instructions that perform encryption. Encryption instructions 128 may require receipt of one of encryption keys 122 to perform the encryption. Encryption instructions 128 may generate a passcode based on encryption keys 122. Alternatively, unsecured system 126 may receive the new passcode from secure module 102 in response to providing the prior passcode that was stored on unsecured system 126. Throughout this specification, other embodiments may be obtained by replacing encryption instructions 128 with instructions to perform a task, and replace any discussion of encryption instruction 128 performing encryption or decryption with the instructions performing that task.

As an example of one embodiment, secure module 102 is a USB internal device, which is a secure device having at least a USB connection for interface 124, internal memory for memory 110, fingerprint sensor for acquisition mechanism 104, and a processor for encryption key circuitry 108. In an embodiment, this device does not run an operating system. All fingerprint data or user information 120 is acquired and stored on the USB internal device.

FIG. 2 shows a block diagram of an example of an unsecured system 200, which may be used in system 100. Unsecured system 200 may include output system 202, input system 204, memory system 206, processor system 208, communications system 212, and input/output device 214. In other embodiments, unsecured system 200 may not include all of the components listed above or include other components in addition to, and/or instead of, those listed above.

Output system 202 may include any one of, some of, any combination of, or all of a monitor system, a handheld display system, a printer system, a speaker system, a connection or interface system to a sound system, an interface system to peripheral devices and/or a connection and/or interface system to a computer system, an intranet, and/or an internet, for example.

Input system 204 may include any one of, some of, any combination of, or all of a keyboard system (e.g., an encryption keyboard), a mouse system, a track ball system, a track pad system, buttons on a handheld system, a scanner system, a microphone system, a connection to a sound system, and/or a connection and/or interface system to a computer system, intranet, and/or internet (e.g., IrDA, USB), for example.

Memory system 206 may include, for example, any one of, some of, any combination of, or all of a long term storage system, such as a hard drive; a short term storage system, such as random access memory; a removable storage system, such as a floppy drive, jump drive or other removable drive; and/or flash memory. Memory system 206 may include one or more machine-readable mediums that may store a variety of different types of information.

The term machine-readable medium is used to refer to any medium capable carrying information that is readable by a machine. One example of a machine-readable medium is a computer-readable medium. Another example of a machine-readable medium is paper having holes that are detected and trigger different mechanical, electrical, and/or logic responses. For example, embedded software is stored on a machine-readable medium. Software versions of any of the components of FIGS. 1-7 may be stored on machine-readable mediums.

Processor system 208 may include any one of, some of, any combination of, or all of multiple parallel processors, a single processor, a system of processors having one or more central processors, and/or one or more specialized processors dedicated to specific tasks.

Communications system 212 communicatively links output system 202, input system 204, memory system 206, processor system 208, and/or input/output system 214 to each other. Communications system 212 may include machine-readable media such as any one of, some of, any combination of, or all of electrical cables, fiber optic cables, long term and/or short term storage (e.g., for sharing data) and/or means of sending signals through air (e.g., wireless communications), for example. Some examples of means of sending signals through air include systems for transmitting electromagnetic waves such as infrared and/or radio waves and/or systems for sending sound waves.

Input/output system 214 may include devices that have the dual function as input and output devices. For example, input/output system 214 may include one or more touch sensitive display screens, which display an image and therefore are an output device and accept input when the screens are pressed by a finger or stylus, for example. The touch sensitive screens may be sensitive to heat and/or pressure. One or more of the input/output devices may be sensitive to a voltage or current produced by a stylus, for example. Input/output system 214 is optional, and may be used in addition to or in place of output system 202 and/or input device 204.

FIG. 3 shows a block diagram of an example of memory 206. Memory 206 may include optional operating system 302, encryption instructions 304, and passcode 306. In other embodiments system memory 206 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Memory 206 may contain optional operating system 302. Some examples of optional operating system 302 are Linux, Unix, Windows, and DOS. However, any other operating system may be used instead, including specialized operating systems such as for cell phones, video game players, other hand held devices, or any other operating system.

Encryption instructions 304 may cause unsecured system 200 to encrypt and/or decrypt items. Encryption instructions 304 may be an embodiment of encryption instructions 128. In an embodiment, encryption instructions 304 will only perform encryption and/or decryption if requested by secure module 102 and/or if secure module sends one of encryption keys 122, thereby granting permission for the encryption to take place.

Passcode 306 is stored by unsecured system 200 and is used to authenticate a request for encoding and/or decoding an item. In an embodiment, passcode 306 is generated by secure module 102, sent to unsecured system 126, and then stored at unsecured system 126 for authentication of a later request for encrypting and/or decrypting data. When it is desired to encrypt or decrypt data, passcode 306 is sent back to secure module 102, and secure module 102 determines whether passcode 306 was the passcode supplied earlier. If passcode 306 is the earlier supplied passcode, secure module 102 sends one of encryption keys 122, which encryption instructions 304 use to encrypt the desired data. In another embodiment, passcode 306 is not used at all.

In still another embodiment, the key K_(d) is encrypted before it is sent from secure module 102 to unsecured system 126. In some encryption schemes, passcode 306 may be used as an encryption key to encrypt key K_(d). For example, if passcode 306 is 256 bits, then AES 256 bit encryption could use passcode 306 as the key and encrypt key K_(d), denoted as E(K_(d)). Then E(K_(d)) is transmitted to unsecured system 126, where the unsecured system 126 executes a AES 256 bit decryption code, and its copy of passcode 306 to decrypt E(K_(d)) so that the unsecured system 126 has possession of key K_(d). Other encryption methods may also be used to securely transmit K_(d) from secure module 102 to unsecured system 126, such as DES, Blowfish, or RSA.

Throughout this specification, other embodiments may be obtained by replacing encryption instructions 304 with instructions to perform a task, and replace any discussion of encryption instruction 304 performing encryption or decryption with the instructions performing that task.

FIG. 4 shows an example of an embodiment of a secure system 400. Secure system 400 includes secure module 402, computer 404 having input system 406 and output system 408. Secure system 400 also includes system 410, network 412, and system 414. In other embodiments secure system 400 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Secure system 400 illustrates some of the variations of the manners of implementing system 100. Secure module 402 is one embodiment of secure module 102. Secure module 402 is capable of being plugged into and communicating with computer 404 or with other systems via computer 404. Secure module 402 may communicate wirelessly with computer 404 in addition to, or instead of, being capable of being plugged into computer 404. A user may use input system 406 and output system 408 to communicate with secure module 102.

Computer 404 is directly connected to system 410, and is connected, via network 412, to system 414. Network 412 may be any one or any combination of one or more Local Area Networks (LANs), Wide Area Networks (WANs), wireless networks, telephones networks, and/or other networks. Unsecured system 126 may be any of, a part of any of, or any combination of any of computer 404, system 410, network 412, and/or system 414. As an example, unsecured system 126 and encryption instructions 128 may be located on computer 404. As yet another example, unsecured system 126 and encryption instructions 128 may both be located on system 414 or may both be located on system 410.

FIG. 5 shows one example of a secure module 500, which may include sensor 502, cover 504, and interface 506. In other embodiments, secure module 500 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Secure module 500 is an example of secure module 102 or 402. Sensor 502 may be a mechanism of acquiring fingerprints, and is an example of acquisition mechanism 104. Cover 504 may be a cover for covering sensor 502, and for protecting sensor 502 when sensor 502 is not in use. Cover 504 may swing open, slide open, and/or snap off and on. Interface 506 is an example of interface 124, and is for connecting with an electronic device, such as a computer. Interface 506 may be a USB port or may be replaced with an RS 232 connection, a wireless connection using RFID, a serial port or any of a number of other types of connections.

FIG. 6 shows an example of a secure module 600. Secure module 600 includes display 602, sensor 604, and cover 606. In other embodiments secure module 600 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Secure module 600 is an embodiment of secure module 102. Secure module 600 may be used instead of secure module 402 in FIG. 4. Display 602 displays passcodes and/or encryption keys, and is an example of interface 124. Display 602 is an interface with which the user interacts with secure module 102, and may be used for transferring the passcode or encryption key to unsecured system 126. Optionally, secure module 600 may also include a transmitter for transmitting the passcode or encryption key via radio waves, light pulses, and/or sound, for example, as part of interface 124. Sensor 604 is an example of acquisition mechanism 104, and maybe for acquiring fingerprints and/or images of other parts of the body of the user. The user may swipe her or his finger over sensor 604. In response, display 602 may display a passcode and/or encryption key that is only good for one use. The user reads the passcode or encryption key and causes the passcode and/or encryption key to be submitted to unsecured system 126. Cover 606 slides over the portion of secure module 600 having sensor 604 to protect sensor 604 from damage when not in use.

FIG. 7 shows an example of a secure module 700, which may include display 702, keypad 704, and sensor 706. In other embodiments secure module 700 may not have all of the components listed above or may have other components instead of and/or in addition to those listed above.

Secure module 700 is an example of secure module 102 (FIG. 1), which may be used instead of secure module 402 in FIG. 4. Display 702 is an example of interface 124, and may display passcodes, encryption keys, status information, instructions, replies to commands, for example. Optionally, secure module 700 may also include a transmitter for transmitting the passcode or encryption key via radio waves, light pulses, and/or sound, for example, as part of interface 124. Keypad 704 is for entering user information and commands, for example, and may be part of acquisition mechanism 104. Sensor 706 may be for acquiring fingerprints and/or images of other parts of the body of the user, and is also part of acquisition mechanism 104. Having both keypad 704 and sensor 706 allows secure module 700 to be configured to require that the user enter identifying information, such as social security number and birthday, in addition to the user data acquired via sensor 706.

Any one of, or any combination of, secure modules 600 and 700 maybe used in place of, or in addition to, secure module 402 within secure system 400, for example. Secure modules 402, 500, 600, and 700 are just a few examples of the many embodiments of secure module 102.

FIG. 8 is a flowchart of an example of a method 800 for assembling secure module 102. In step 802, secure area 106 (FIG. 1) is assembled, which may include installing memory 110 onto encryption key circuitry 108. In step 804, the acquisition mechanism 104 (FIG. 1) is coupled to the secure area 106. In step 806, interface 124 (FIG. 1) is coupled to secure area 106. In step 808, instructions 112 and/or other instructions are installed. In step 810, secure area 106, acquisition mechanism 104, and interface 124 are enclosed within a housing that is small enough to fit within a user's hand (e.g., shorter than a typical pen and no more than a two or three times wider than a typical pen). For example, the housing may be 2 to 6 inches long and less than a half inch in diameter. The secure module 102 may be of a size that is comparable to a thumb print. In other words, secure module 102 only needs to be large enough to accept user information. In embodiments where the user information is fingerprints, the secure module 102 could be the size of a portion of a thumb large enough to capture a thumb print during a swipe, for example. In embodiments where acquisition mechanism 104 is a camera, secure module 102 does not need to be much larger than a small camera. In an embodiment, secure module 102 is less than 6 inches, less than 2 inches, less than an inch, or less than a centimeter in size. In some embodiments, the user information may be something that the user knows. For example, a birthday may be entered with a button or keyboard that is on the secure module. Or as another example, PIN 5783 may be entered. In some embodiments, part of the acquisition mechanism could have a left, right, up and down arrows and a middle “select” button similar to a mobile phone. This enables the user to read on a display screen what letter, number, other character or even a word that they might want to select. They might even select an image as something that they know. What they know may independent of “what they are” as in a fingerprint or a camera that takes a picture of them. Or entering “what they know” may be entered into secure module 102 in addition to “what they are” such as a fingerprint.

In step 810, encryption instructions 128 are installed on unsecured system 126. Step 810 may be performed at any time with respect to steps 802-808. In other embodiments method 800 may not have all of the steps listed above or may have other steps instead of and/or in addition to those listed above. Additionally, the steps of method 800 may be performed in other orders, may not be distinct steps, and/or many of the steps may be performed concurrently with one another. Additionally the steps of method 800 may not be distinct steps.

FIG. 9 shows a flowchart of an example of a method 900 of setting up system 100. During method 900 in step 904 user data is acquired. Acquiring user data may involve a user entering data and/or acquisition mechanism 104 sensing biometric information. Step 904 may also involve encryption key circuitry 108 executing acquire data 114 and store user data 118, thereby causing encryption key circuitry 108 to transfer the user data from acquisition mechanism 104 to memory 110 and store the user data at memory 110.

In step 906, the acquired user data is passed to, inside of the secure module 102, to a one-way hash function or another type of one-way method of encoding user data. In step 908, generate encryption keys 123 is executed, and the one-way method generates an encryption key, K_(d). In step 910, on secure module 102, the encryption key, K_(d) is passed to a one-way hash function or another type of one-way method Φ. In step 912, the value P_(d)=Φ(K_(d)), a passcode, is computed on secure module 102 and subsequently, in step 914, passcode P_(d) is transmitted to unsecured system 126. In step 916, unsecured system 126 stores passcode P_(d). If an intruder finds passcode P_(d) on unsecured system 126, the information obtained from passcode P_(d) is not helpful to the intruder, because the inverse of the encoding function, Φ⁻¹ is computationally difficult to compute.

Steps 902-914 may involve executing other instructions of instructions 112 in addition to, or instead of, those that appear in FIG. 1. Step 810 could be performed as part of method 900 instead of as part of method 800. Other embodiments may not include all of the above steps and/or may include other steps in addition to or instead of those listed in method 900. Additionally the steps listed in method 900 may not be distinct steps.

FIG. 10 shows a flowchart of an example of a method 1000 for encrypting or decrypting data. In step 1002, encryption key circuitry 108 makes a request to the unsecured system 126 to encrypt or decrypt some data. The request may be in response to a user entering user data (e.g., the user scanning a fingerprint into authentication mechanism 104), and the user data being authenticated. In step 1004, unsecured system 126 sends the passcode P_(d) to the secure module 102. In step 1006, secure module 102 authenticates the unsecured system 126, by checking whether passcode P_(d) is correct. If passcode P_(d) is not correct, then in step 1007 method 1000 is terminated. Consequently, encryption key K_(d) is not passed to unsecured system 126. The reason for not passing encryption key K_(d) is because it is expected that an intruder program is running and attempting to perform the encryption or decryption.

Returning to step 1006, if passcode P_(d) is correct, then in step 1008 secure module 102 retrieves encryption key K_(d) from memory 110 (e.g., flash memory) and transmits encryption key K_(d) to unsecured system 126. In another embodiment, step 1008 may involve encrypting encryption key K_(d) before sending encryption key K_(d) from secure module 102 to unsecured system 126. For example, passcode 306 may be used as an encryption key to encrypt encryption key K_(d). If passcode 306 is 256 bits, then AES 256 bit encryption could use passcode 306 as the encryption key and encrypt encryption key K_(d). The encrypted encryption key may be denoted by E(K_(d)). Then the encrypted encryption E(K_(d)) is transmitted to unsecured system 126.

In step 1010, unsecured system 126 receives (e.g., accepts) encryption key K_(d). Receiving encryption key K_(d), may involve receiving encrypted encryption key E(K_(d)). Additionally, step 1010 may involve unsecured system 126 executing an AES 256 bit decryption code, using the copy of passcode 306 stored at unsecured system 126 to decrypt E(K_(d)) so that unsecured system 126 has possession of key K_(d). Other encryption methods may also be used to securely transmit K_(d) from secure module 102 to unsecured system 126, such as DES, Blowfish, or RSA.

In step 1012, unsecured system 126 uses encryption key K_(d) to encrypt or decrypt the data. In step 1014, encryption key K_(d) is discarded. Encryption key K_(d) is not stored on unsecured system 126; encryption key K_(d) only remains in the volatile memory of unsecured system 126 for a brief period of time. Immediately, after the encryption or decryption process is finished making use of encryption key K_(d), the volatile memory, which contains encryption key K_(d), is erased. Encryption key K_(d) may be erased using any of several methods. For example, a value containing no information, such as the number 0, written at the one or more memory locations where encryption key K_(d) was located. As another example, a value containing information that is unrelated to encryption key K_(d) is written in the location where encryption key K_(d) was located. Since encryption key K_(d) is in the unsecured system 126, which is not secure, for only a short while, it is difficult for an intruder to copy encryption key K_(d). Other embodiments may not include all of the above steps and/or may include other steps in addition to or instead of those listed in method 1000. Additionally the steps listed in method 1000 may not be distinct steps.

Method 1100 shows an embodiment of the invention. In step 1102, at the unsecured device, receiving from the secured module a request to perform an action that requires authorization. In step 1104, in response to the receiving, the unsecured system sends a first passcode to the secure module. In step 1105 a, the unsecured device checks whether passcode is correct. In step 1105 b, if the passcode is not correct the method ends. In step 1106, in reply to the sending of the first passcode, if the first passcode is correct, at the unsecured system receiving a first encryption key from the secure module. In step 1108, in response to receiving at the unsecured system the first encryption key, encrypting or decrypting data with the first encryption key, and generating a second passcode, that is different from the first passcode, by at least applying a function to the first encryption key. In step 1110, at the unsecured system, erasing the first passcode and replacing the first passcode with the second passcode. Also in step 1110, after the encrypting or decrypting of the data is complete and before a second encryption key is received at the unsecured device, erasing the first encryption key at the unsecured system.

Each embodiment disclosed herein may be used or otherwise combined with any of the other embodiments disclosed. Any element of any embodiment may be used in any embodiment.

Although the invention has been described with reference to specific embodiments, it will be understood by those skilled in the art that various changes may be made and equivalents may be substituted for elements thereof without departing from the true spirit and scope of the invention. In addition, modifications may be made without departing from the essential teachings of the invention. 

1. A machine-implemented method comprising: receiving a first access key from a secure module at a host system having a processor system including at least one processor and memory unit including at least one computer readable medium; performing, by at least one processor of the host system, a first action that requires the access key as a part of performing the action for the action to be performed properly; erasing, the processor system of the host system, the access key from the host system prior to receiving a second access key; and receiving, at the host system, a second access key from the secure module, the second access key being different than the first access key; each access key is derived from a prior access key, the first access key being based on biometric information.
 2. The method of claim 1, further comprising: prior to receiving the first access key, receiving from the secure module a request for the host system to perform the action.
 3. The method of claim 2, further comprising: in response to the receiving of the request to perform the first action, sending a stored copy of a passcode from the host system to a module from which the request originated for authentication at the secure module; the receiving of the first access key occurring as a result of the passcode being authenticated.
 4. The method of claim 3, further comprising: at the host system generating a new passcode, based on the first access key, for authenticating the host system at the secure module.
 5. The method of claim 4, further comprising: storing the new passcode in the memory unit of the host system.
 6. The method of claim 4, the generating occurring automatically in response to receiving the encryption key.
 7. The method of claim 4, the generating including at least applying a function to the access key, therein obtaining the new passcode.
 8. The method of claim 3, wherein the receiving of the access key at the host system is in response to the sending of the stored passcode to the secure system for authentication at the secure system.
 9. The method of claim 1, wherein the performing of the first action includes at least executing one or more encryption instructions based on the first access key.
 10. The method of claim 1, wherein the first access key received is encrypted, and the method further comprises decrypting the first access key received.
 11. The method of claim 10, the received first access key being encrypted only with the passcode further comprising decrypting the first access key with only the passcode.
 12. The method of claim 10, the received first access key being encrypted with the passcode further comprising decrypting the first access key with the passcode.
 13. The method of claim 1, no personal data is stored by the method other than a passcode.
 14. The method of claim 1, the method does not store keys other than access keys, and the access key is only kept during a period of time in which the access key is in use.
 15. The method of claim 1, the receiving includes at least receiving the access key from a self-contained user device.
 16. The method claim 1, the method does not require the use of a public-private key pair.
 17. The method of claim 1, the first access key being based on user information, and each subsequent access key being derived from a prior access key, and thereby being based on the user information.
 18. A machine-implemented method comprising: receiving from a secure module a request to execute one or more encryption instructions at a host system; in response, sending a stored passcode to the secure module from which the request originated; receiving at the host system an access key from the secure module if the passcode is authenticated at the secure module; generating, by a processor system of the host system, a new passcode based on the access key; executing, by the host system, the one or more encryption instructions based on the access key; erasing the access key from the host system; erasing the stored passcode from the host system; and storing the new passcode at the host system.
 19. The method of claim 18, the receiving of the access key being in reply to the sending of the stored passcode.
 20. The method of claim 18, the erasing of the access key being performed after using the access key for the executing.
 21. A machine-implemented method comprising: after a host system is set up, receiving from a user device a request to perform an action that requires an access key, the host system including at least a memory system and a processor system having at least one processor; in response the request, sending a passcode for authentication; receiving the access key from the user device at the host system if the passcodes is authenticated by the user device; performing, by the processor system, the action that requires the access key; and erasing the access key from the memory system.
 22. A method comprising: after an unsecured device and a secured module are set up, receiving at the unsecured device from the secured module a request to perform an action that requires authorization; in response to the receiving, the unsecured system sends a first passcode to the secure module; in reply to the sending of the first passcode, if the first passcode is correct, receiving at the unsecured system a first encryption key from the secure module; in response to receiving at the unsecured system the first encryption key, encrypting or decrypting data with the first encryption key, and generating a second passcode, that is different from the first passcode, by at least applying a function to the first encryption key; at the unsecured system, erasing the first passcode and replacing the first passcode with the second passcode; and after the encrypting or decrypting of the data is complete and before a second encryption key is received at the unsecured device, erasing the first encryption key at the unsecured system; the first encryption key and second encryption key are different values that are based on one or more values that results from applying a function to biometric information, the function being one for which computing an inverse is computationally intractable.
 23. The method of claim 22, the encryption key received is encrypted, and the method further comprising decrypting the encryption key received.
 24. A machine-implemented method comprising: receiving an access key, at a host system, from a secure module; performing, by a processor system of the host system, an action that requires the access key as a part of performing the action for the action to be performed properly, the processor system having at least one processor; and erasing the access key from the host system prior to receiving a next access key; the access key is based on a value that results from applying a function to user information that is expected to be unique to the user, the function being one for which computing an inverse is computationally intractable; each access key is derived from a prior access key, the first access key being based on biometric information.
 25. A method comprising: after an unsecured device and a secured module are set up, receiving at the unsecured device from the secured module a request to perform an action that requires authorization; in response to the receiving, the unsecured system sends a first passcode to the secure module; in reply to the sending of the first passcode either a first encryption key is received from the secure module indicating that the first passcode was correct or the first encryption key is not received from the secure module indicating that the first passcode is not correct; if a first encryption key is received at the unsecure system from the secure module, in response to receiving at the unsecured system the first encryption key, encrypting or decrypting data with the first encryption key, and generating a second passcode, that is different from the first passcode, by at least applying a function to the first encryption key; at the unsecured system, erasing the first passcode and replacing the first passcode with the second passcode; and after the encrypting or decrypting of the data is complete and before a second encryption key is received at the unsecured device, erasing the first encryption key at the unsecured system; the first encryption key and second encryption key are different values that are based on one or more values that results from applying a function to biometric information, the function being one for which computing an inverse is computationally intractable. 